//Hey, check mo_hq_ev3 for putting equipfialure cmd in there! //also the SWAP tag should be changed // Fly to Deneba VI and back // Author : Imergy, Script Translator L.Tietz // July 25&26, 1998 psm // ========================================================= // Goal Phase // MISSION GOAL STATEMENT (REQUIRED) // The format for DES = locH locV locName // ========================================================== // Initial Phase // INITIAL CMD (REQUIRED) // ========================================================== // Execute Phase // Triggered when ship processes #executeGoal command. // (REQUIRED) // ========================================================== // Close Mission Phase #closeMission // We want to set our destination to Starbase and head home // ========================================================== // The following TAGS are Mission Overlay Tags. Each one has a special purpose and meaning. // // Your shields can malfunction. This could occur do to substaining a HIT from an object // or enemy fire or from ware-n-tear. Since this event is asycron with the main mission script // we need a way to give the script writer some control over how the ship will // respond to this event. In the following case we chose to display // a head quarter dialog box. // Notice we are issuing a Head Quarters Dialog cmd here - this command MUST have a // corresponding HEAD QUARTERS Dialog definition created for it. See // the end of this script for the HEAD QUARTER defs. // The following TAGS are used to communicate a response to the starship // when it encounters an alien ship // We engage the alien in debate and they respond with friendship // We engage the alien in debate and they respond with hostility // We engage the alien in debate and they respond with an attack // We are in battle with the enemy ship and we have destroyed it // We are in battle with the enemy ship and we have disabled it // We are in battle with the enemy ship and we have made a small impact on it // We are in battle with the enemy ship and we have given it a slight dent // We are in battle with the enemy ship and we have not had an effect on the ship // If durring a confict the target ship is deemed invincible the conflict res obj will issue // a cmd to the ship. We need to tell the overlay data obj the cmd that it will send to // the ship in this occurence. In this specific case we want to tell the overlay obj to // issue the cmd #HQCmd1. This cmd is defined below to trigger a HQ request dialog. // HQ Dialog Box Data // You can put an cmds and // text MSGs in the data field. The format is as follows: // ShipMessageSTR ,cmd1, Option1STR , cmd2 , Option2STR , cmdID , // The cmdID is used by the ship to store and retrive the other fields from the // overlay data OBJ. // The first Tag is REQUIRED. This Tag tells the mission sim overlay OBJ how many HQ messages // it must read. If you will not make use of the Head Quarter Dialog Box then you // will set MO_HQ_EV0 = 0. If you set the value to > 0 then you must provide the // tags for each dialog box that you wish to have displayed. making use of the // MSG Table // Rev July 1 98 --psm 98/07/26&28 × for msg99 goals // This table is used for readablity and maintainablity of all message MSGs. // Message MSGs can be used as part of any MCO. // Execute Mission Cmd MSGs // was in MSG13 // Close Mission Cmd MSGs // ENVIRONMENT OVERLAY DATA -- This data will be moving to it's own file // This TAG is used to define a set of up to 10 events that will be triggered // by the ship crossing a specific point on the map during a mission. You must select // an event from the lEvent tag table and a point value from 0 to 1000 // This TAG is used to define a set of up to 10 events that will be triggered // at specific times relative to the start of a mission. You must select // an event from the tEvent tag table and a delta t value in ticks (60 ticks / sec) // The following set of tags are related to scans conducted by the starship. When the starship // conducts a scan it will communicate with the overlay data obj to get a response. You must // provide the responses to all possibilities to all scan types within a two dimensional space. // The format for an scan-environment tag is as follows // // Where L=Left Org, T=TopOrg, R=RightOrg, BOrg=BottomOrg and define a Rectangle Target for the scan // All Scan Result Tags must be DEFINED (REQUIRED). // Only the TAGS that will be triggered by a scan request cmd that you have // included within an execute type tag need to be defined with specific data. // For the ones that I'm not using I have placed a single null Rect with a null cmd and message data // is a long range scan // is a freq (RF) scan // is a Partical Spectrometry scan // is a Gravimetric Scan // is a Proton Spec Scan // is a Life Form Scan // is a Sub-Space Scan // is a Optical Scan // is a Graviton Flux Scan // is a Gamma Radiation Scan // is a InfraRed Scan // is a Particle Map Scan